Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a29b54e333f55d4bbc33fb333671d2f0700a10baf005575938a335b3cde4f23

Tx prefix hash: 95ff0ef05b33c71fe0bebcb10f22cec23611794c449f37374cd1a44c999e2e27
Tx public key: f7e3c3e4bbd066b117be577febfdd7d8ff7e2edae6712d1981a5b4ba7c1eedf6
Timestamp: 1710171279 Timestamp [UCT]: 2024-03-11 15:34:39 Age [y:d:h:m:s]: 01:063:22:42:54
Block: 976079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306721 RingCT/type: yes/0
Extra: 01f7e3c3e4bbd066b117be577febfdd7d8ff7e2edae6712d1981a5b4ba7c1eedf60211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eff03f73a24e59f880502d534ecb8445c56fd9224d8ad29cc59e010159c72f08 0.600000000000 1436066 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": 976089, "vin": [ { "gen": { "height": 976079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eff03f73a24e59f880502d534ecb8445c56fd9224d8ad29cc59e010159c72f08" } } ], "extra": [ 1, 247, 227, 195, 228, 187, 208, 102, 177, 23, 190, 87, 127, 235, 253, 215, 216, 255, 126, 46, 218, 230, 113, 45, 25, 129, 165, 180, 186, 124, 30, 237, 246, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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