Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cba54940fc1f80da5468535b978b1297bfaace67ed673574b17ec01470a881c

Tx prefix hash: 552b9a6ebe13f6307817cf945111891f2d3a2378d8a5e6d4b8a8a26a707315a5
Tx public key: 59fcd814f9f3e6d6485842d20494a96a9b3d729d7683e56ab910390829c37862
Timestamp: 1709340724 Timestamp [UCT]: 2024-03-02 00:52:04 Age [y:d:h:m:s]: 01:070:14:19:19
Block: 969191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311480 RingCT/type: yes/0
Extra: 0159fcd814f9f3e6d6485842d20494a96a9b3d729d7683e56ab910390829c3786202110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0e8397a83490d8d91b696da64210650f3d05d3aa0086dde1d7d400084a91242 0.600000000000 1429020 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": 969201, "vin": [ { "gen": { "height": 969191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0e8397a83490d8d91b696da64210650f3d05d3aa0086dde1d7d400084a91242" } } ], "extra": [ 1, 89, 252, 216, 20, 249, 243, 230, 214, 72, 88, 66, 210, 4, 148, 169, 106, 155, 61, 114, 157, 118, 131, 229, 106, 185, 16, 57, 8, 41, 195, 120, 98, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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