Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad92105d22e6ddf7af289d5597a38161410ef6de896a4e5536c8da5c81934cb7

Tx prefix hash: 3c2eeedea8e136838586397f3a7825630dbfb2090b68f872d5aa42782900f3ab
Tx public key: a8ef76c50e0ab8d43705759f3b74d421bfcdf6a04a3171c5ceecf7af13824a33
Timestamp: 1706236228 Timestamp [UCT]: 2024-01-26 02:30:28 Age [y:d:h:m:s]: 01:279:16:38:23
Block: 943417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458711 RingCT/type: yes/0
Extra: 01a8ef76c50e0ab8d43705759f3b74d421bfcdf6a04a3171c5ceecf7af13824a3302110000000f59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f525adb9a2663836a3d3280c037db241bb1cf7faf1552571d34ccbaa0841d4e2 0.600000000000 1401623 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": 943427, "vin": [ { "gen": { "height": 943417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f525adb9a2663836a3d3280c037db241bb1cf7faf1552571d34ccbaa0841d4e2" } } ], "extra": [ 1, 168, 239, 118, 197, 14, 10, 184, 212, 55, 5, 117, 159, 59, 116, 212, 33, 191, 205, 246, 160, 74, 49, 113, 197, 206, 236, 247, 175, 19, 130, 74, 51, 2, 17, 0, 0, 0, 15, 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