Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c552c0ee18d7bf50553861bf8fcee646cfff1afd7a4462e9623e249becb6dc4

Tx prefix hash: 145acb6bd804e1c4215448e8a7280512a0ab4607a2506fc583d1c24e6212962a
Tx public key: afb36c0066f70add48d30f00cb50d6a0199c8781ba464b42b66943e64c0f7315
Timestamp: 1722091329 Timestamp [UCT]: 2024-07-27 14:42:09 Age [y:d:h:m:s]: 01:102:10:20:10
Block: 1074893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331690 RingCT/type: yes/0
Extra: 01afb36c0066f70add48d30f00cb50d6a0199c8781ba464b42b66943e64c0f731502110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b8fe6898dc4e4ccdc4e8ce3b49a7760da8273aa0dca52910e75b9af8dd70f52 0.600000000000 1547412 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": 1074903, "vin": [ { "gen": { "height": 1074893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b8fe6898dc4e4ccdc4e8ce3b49a7760da8273aa0dca52910e75b9af8dd70f52" } } ], "extra": [ 1, 175, 179, 108, 0, 102, 247, 10, 221, 72, 211, 15, 0, 203, 80, 214, 160, 25, 156, 135, 129, 186, 70, 75, 66, 182, 105, 67, 230, 76, 15, 115, 21, 2, 17, 0, 0, 0, 14, 233, 20, 221, 21, 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