Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8172b802dbf60272b4781a39c1b31cff9ac64ca2e78de5ca2ad2ea89181de8de

Tx prefix hash: 222c6e2f608d3e9e29e59a1af96d3569b5811e3bcd87b8a60b5ed31a2a0350c0
Tx public key: 264d37aae93b5dfb87ef51bf54bd84f0201806d1ed4793bba0e23f16b572f89e
Timestamp: 1741003873 Timestamp [UCT]: 2025-03-03 12:11:13 Age [y:d:h:m:s]: 00:255:20:39:17
Block: 1231224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180616 RingCT/type: yes/0
Extra: 01264d37aae93b5dfb87ef51bf54bd84f0201806d1ed4793bba0e23f16b572f89e0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70a1820877b53affa4f30a617fec6ea4474366cc90e0a1c1c53c301677b33637 0.600000000000 1718131 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": 1231234, "vin": [ { "gen": { "height": 1231224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70a1820877b53affa4f30a617fec6ea4474366cc90e0a1c1c53c301677b33637" } } ], "extra": [ 1, 38, 77, 55, 170, 233, 59, 93, 251, 135, 239, 81, 191, 84, 189, 132, 240, 32, 24, 6, 209, 237, 71, 147, 187, 160, 226, 63, 22, 181, 114, 248, 158, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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