Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16aed810b3117057e496981742c322eacf8ba67aae198b5844e739d62291f236

Tx prefix hash: e6be1e2eb6579016a3b5f25df136e195eec26ac71350964e1e4c7a8a8e8d64a8
Tx public key: dcc514da6569e475eb2ab968678e9b3553bf9ec676af1b4ce0b1bb36766c53bb
Timestamp: 1743737343 Timestamp [UCT]: 2025-04-04 03:29:03 Age [y:d:h:m:s]: 00:236:14:19:21
Block: 1253846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166860 RingCT/type: yes/0
Extra: 01dcc514da6569e475eb2ab968678e9b3553bf9ec676af1b4ce0b1bb36766c53bb0211000000034060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c0b428d67634be4fec804f2c31f582a5a80339881f7de704a00d3d712635e3e 0.600000000000 1740927 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": 1253856, "vin": [ { "gen": { "height": 1253846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c0b428d67634be4fec804f2c31f582a5a80339881f7de704a00d3d712635e3e" } } ], "extra": [ 1, 220, 197, 20, 218, 101, 105, 228, 117, 235, 42, 185, 104, 103, 142, 155, 53, 83, 191, 158, 198, 118, 175, 27, 76, 224, 177, 187, 54, 118, 108, 83, 187, 2, 17, 0, 0, 0, 3, 64, 96, 246, 210, 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