Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6025e54ecb93e1eebd63772310755c9f6bd31c9bcb41f1fdec0664244a5a67da

Tx prefix hash: 00fec94f4048a1c3c4890dc6ce6e171f85d5d0406d44dcd4d1644b02dd86f618
Tx public key: 60596da8b1852d8f530980d61ad66f9794dab4e4aef1dc6f6963f8746e6cf714
Timestamp: 1729588974 Timestamp [UCT]: 2024-10-22 09:22:54 Age [y:d:h:m:s]: 00:178:08:40:55
Block: 1137023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127285 RingCT/type: yes/0
Extra: 0160596da8b1852d8f530980d61ad66f9794dab4e4aef1dc6f6963f8746e6cf714021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cb50ea3eff1717ee5e8d0d06a2af870d7314eb572f03ce2d310e1872e0e7f89 0.600000000000 1620436 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": 1137033, "vin": [ { "gen": { "height": 1137023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cb50ea3eff1717ee5e8d0d06a2af870d7314eb572f03ce2d310e1872e0e7f89" } } ], "extra": [ 1, 96, 89, 109, 168, 177, 133, 45, 143, 83, 9, 128, 214, 26, 214, 111, 151, 148, 218, 180, 228, 174, 241, 220, 111, 105, 99, 248, 116, 110, 108, 247, 20, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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