Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 960e2572b24d81628f76ad72cfacdf176c0cfef7902fdbea45fef63e4dbb5a1c

Tx prefix hash: bd30e28744d49fa162039cd62f2c8677f7d419882a2a434c3eecfd97d70d659b
Tx public key: 66f5114df22fef3752a416ecce1a25b7f6f441788567e70f448c1d78f5eddfd7
Timestamp: 1640618126 Timestamp [UCT]: 2021-12-27 15:15:26 Age [y:d:h:m:s]: 03:308:15:54:35
Block: 404667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 997103 RingCT/type: yes/0
Extra: 0166f5114df22fef3752a416ecce1a25b7f6f441788567e70f448c1d78f5eddfd7021100000032edb0d4a3000000000000000000

1 output(s) for total of 28.000809590000 dcy

stealth address amount amount idx
00: 4ba253ddccff46455043b94d686d9cf3534e830e38eccf5920c7b00096997178 28.000809590000 804844 of 0

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": 404677, "vin": [ { "gen": { "height": 404667 } } ], "vout": [ { "amount": 28000809590, "target": { "key": "4ba253ddccff46455043b94d686d9cf3534e830e38eccf5920c7b00096997178" } } ], "extra": [ 1, 102, 245, 17, 77, 242, 47, 239, 55, 82, 164, 22, 236, 206, 26, 37, 183, 246, 244, 65, 120, 133, 103, 231, 15, 68, 140, 29, 120, 245, 237, 223, 215, 2, 17, 0, 0, 0, 50, 237, 176, 212, 163, 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