Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feff7980e48862e7741713c6daa09aecb032fd6cd7e77b1b16f6170a011d2a26

Tx prefix hash: 5b685cdec5a330693c6a80717c5def07589362e9ac45ac59f6c487de4978ae9c
Tx public key: 59c9a01bf45060f8bdfb98bf9a689a5e1574127dbad8490f6987d932e4c746b2
Timestamp: 1738384286 Timestamp [UCT]: 2025-02-01 04:31:26 Age [y:d:h:m:s]: 00:333:14:53:19
Block: 1209540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236267 RingCT/type: yes/0
Extra: 0159c9a01bf45060f8bdfb98bf9a689a5e1574127dbad8490f6987d932e4c746b2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3710741f967d881c71fb53a6fbfbcbc1d4e093eaae35f656414adfcda8521475 0.600000000000 1696285 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": 1209550, "vin": [ { "gen": { "height": 1209540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3710741f967d881c71fb53a6fbfbcbc1d4e093eaae35f656414adfcda8521475" } } ], "extra": [ 1, 89, 201, 160, 27, 244, 80, 96, 248, 189, 251, 152, 191, 154, 104, 154, 94, 21, 116, 18, 125, 186, 216, 73, 15, 105, 135, 217, 50, 228, 199, 70, 178, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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