Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d702a1ef35cdf9d9193106e1d216dd2c1a1f565e561357586e17c1f8ed83001

Tx prefix hash: 98c93500047e553c4d3d98e12bf00fccbf1a88226171687a3017df3661797ef2
Tx public key: 0b18c6f9323d2fce35b073fa318f5717a9a212ee103f974afa282668e3eb6ac8
Timestamp: 1732572456 Timestamp [UCT]: 2024-11-25 22:07:36 Age [y:d:h:m:s]: 00:142:07:25:58
Block: 1161686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101520 RingCT/type: yes/0
Extra: 010b18c6f9323d2fce35b073fa318f5717a9a212ee103f974afa282668e3eb6ac80211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 861c7cd41922a3573b0a5ccd59d459de8f77fc6b717eee943bc2d97ce2a4e146 0.600000000000 1647341 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": 1161696, "vin": [ { "gen": { "height": 1161686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "861c7cd41922a3573b0a5ccd59d459de8f77fc6b717eee943bc2d97ce2a4e146" } } ], "extra": [ 1, 11, 24, 198, 249, 50, 61, 47, 206, 53, 176, 115, 250, 49, 143, 87, 23, 169, 162, 18, 238, 16, 63, 151, 74, 250, 40, 38, 104, 227, 235, 106, 200, 2, 17, 0, 0, 0, 5, 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