Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7877dde8f0966287b44e8069a2b515fbd931da36a6589ed04ac19c52f7d3c45b

Tx prefix hash: 24c50c8cf5a525c3f82ecc60ee982b79c47ac7748f3633631bd50ea9f72f991f
Tx public key: 3a947890f004c54f1e167c735ec50c98c597ae08fa03dad5b97e956bfeac4d8f
Timestamp: 1704477857 Timestamp [UCT]: 2024-01-05 18:04:17 Age [y:d:h:m:s]: 01:123:21:46:37
Block: 928854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349682 RingCT/type: yes/0
Extra: 013a947890f004c54f1e167c735ec50c98c597ae08fa03dad5b97e956bfeac4d8f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f45e150aa37819c8a64b8f8f43ce1638cce47c6a22a8064b74e0501b2297bd1b 0.600000000000 1386718 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": 928864, "vin": [ { "gen": { "height": 928854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f45e150aa37819c8a64b8f8f43ce1638cce47c6a22a8064b74e0501b2297bd1b" } } ], "extra": [ 1, 58, 148, 120, 144, 240, 4, 197, 79, 30, 22, 124, 115, 94, 197, 12, 152, 197, 151, 174, 8, 250, 3, 218, 213, 185, 126, 149, 107, 254, 172, 77, 143, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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