Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9380b472b62fc6cf3f01b445c2544c826ac0ed7da96eb445546d541bd0d5ac2e

Tx prefix hash: 937d7714ad6e8bb62abdacb5c2f13e725326a69dd13d9655e20709119895ceda
Tx public key: 1ac828dd44f66b624319c36f2b5cb50a4ae3fcfc55a7c0194f9ce87b5e309f63
Timestamp: 1718414854 Timestamp [UCT]: 2024-06-15 01:27:34 Age [y:d:h:m:s]: 00:333:06:12:20
Block: 1044419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238177 RingCT/type: yes/0
Extra: 011ac828dd44f66b624319c36f2b5cb50a4ae3fcfc55a7c0194f9ce87b5e309f630211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3447d736244db6ab601b0bb090dd196477c7757546e08ee9ccb5f98efcf59cd0 0.600000000000 1513724 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1044429, "vin": [ { "gen": { "height": 1044419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3447d736244db6ab601b0bb090dd196477c7757546e08ee9ccb5f98efcf59cd0" } } ], "extra": [ 1, 26, 200, 40, 221, 68, 246, 107, 98, 67, 25, 195, 111, 43, 92, 181, 10, 74, 227, 252, 252, 85, 167, 192, 25, 79, 156, 232, 123, 94, 48, 159, 99, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8