Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25dfd6042f7959841da7e09cbea326456bc97816160b88d191f045b79a484112

Tx prefix hash: 3686e8c504a6cbf4db743a2574f04b0f652c94111a18fb4e4dee1baeda991918
Tx public key: 0b33ad6b38bd8372bd6024cf2a881df15538efaf0dc69e233439c1b0b5a64378
Timestamp: 1706241458 Timestamp [UCT]: 2024-01-26 03:57:38 Age [y:d:h:m:s]: 00:293:21:37:14
Block: 943463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210454 RingCT/type: yes/0
Extra: 010b33ad6b38bd8372bd6024cf2a881df15538efaf0dc69e233439c1b0b5a6437802110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2cbb96e3c305acb063a9f6f2817644f3f8dd5c8fdbf897bef309a99eebfe2d5 0.600000000000 1401669 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": 943473, "vin": [ { "gen": { "height": 943463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2cbb96e3c305acb063a9f6f2817644f3f8dd5c8fdbf897bef309a99eebfe2d5" } } ], "extra": [ 1, 11, 51, 173, 107, 56, 189, 131, 114, 189, 96, 36, 207, 42, 136, 29, 241, 85, 56, 239, 175, 13, 198, 158, 35, 52, 57, 193, 176, 181, 166, 67, 120, 2, 17, 0, 0, 0, 4, 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