Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 958cf445c8e4530b5d35e03953bd46f674ba0a55115a8591d299facc6cc6f2c1

Tx prefix hash: 7912f88631159c072c9570eafbe7ec22966a2680a3be7778084ea7fd81f209d4
Tx public key: 918ce97ba7cfd0293a0182d3a441087b23dafb9e7075bb9994d9f223a78783d4
Timestamp: 1720375745 Timestamp [UCT]: 2024-07-07 18:09:05 Age [y:d:h:m:s]: 00:318:06:23:26
Block: 1060670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227446 RingCT/type: yes/0
Extra: 01918ce97ba7cfd0293a0182d3a441087b23dafb9e7075bb9994d9f223a78783d4021100000013e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8845fad7104aedfeae5aa5e56880d9a4fbcae88db1d25f880d5185f0f0f68680 0.600000000000 1531155 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": 1060680, "vin": [ { "gen": { "height": 1060670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8845fad7104aedfeae5aa5e56880d9a4fbcae88db1d25f880d5185f0f0f68680" } } ], "extra": [ 1, 145, 140, 233, 123, 167, 207, 208, 41, 58, 1, 130, 211, 164, 65, 8, 123, 35, 218, 251, 158, 112, 117, 187, 153, 148, 217, 242, 35, 167, 135, 131, 212, 2, 17, 0, 0, 0, 19, 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