Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe259cc5b61d8d7c703534d05c9353e2778919ed4b0ec0216be6fc679bcf3ef7

Tx prefix hash: 9aa4ea42dbff5c83bc32081e27c8c714768e5af47e29eaef6fb9e36c96820640
Tx public key: 27c6cd325322c8ecc370b5767d4644ec95118d12c777e0dc40ae94e9b837a544
Timestamp: 1725965327 Timestamp [UCT]: 2024-09-10 10:48:47 Age [y:d:h:m:s]: 00:211:21:40:04
Block: 1107011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151283 RingCT/type: yes/0
Extra: 0127c6cd325322c8ecc370b5767d4644ec95118d12c777e0dc40ae94e9b837a544021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1880bd8a318aa1507e1b876bc236e0a7fc78310c433dfaa59a7e31ecb7b6e791 0.600000000000 1584618 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": 1107021, "vin": [ { "gen": { "height": 1107011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1880bd8a318aa1507e1b876bc236e0a7fc78310c433dfaa59a7e31ecb7b6e791" } } ], "extra": [ 1, 39, 198, 205, 50, 83, 34, 200, 236, 195, 112, 181, 118, 125, 70, 68, 236, 149, 17, 141, 18, 199, 119, 224, 220, 64, 174, 148, 233, 184, 55, 165, 68, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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