Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f84fbcea06f6ff3cacbce006642e2ba199d93f4c17425e32d4313fb83499abf

Tx prefix hash: 8d67ac20c8059b24ba101deebb415fd8b0aeb6b0e38d3d5ff65354ea08de1814
Tx public key: 2854b8f8b6d1b16a2f984d8e4b43af34a2f6cf0a08aea8efcf6df7c6bb7dd959
Timestamp: 1712742100 Timestamp [UCT]: 2024-04-10 09:41:40 Age [y:d:h:m:s]: 00:351:17:15:51
Block: 997361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251473 RingCT/type: yes/0
Extra: 012854b8f8b6d1b16a2f984d8e4b43af34a2f6cf0a08aea8efcf6df7c6bb7dd9590211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9307e8adc40ac09c1cc51e1a1a4f32ec8337affd87c71ed45b1c9a6753628895 0.600000000000 1457791 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": 997371, "vin": [ { "gen": { "height": 997361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9307e8adc40ac09c1cc51e1a1a4f32ec8337affd87c71ed45b1c9a6753628895" } } ], "extra": [ 1, 40, 84, 184, 248, 182, 209, 177, 106, 47, 152, 77, 142, 75, 67, 175, 52, 162, 246, 207, 10, 8, 174, 168, 239, 207, 109, 247, 198, 187, 125, 217, 89, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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