Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34666909e712e96502484dd1eb2bce578bca54e62ab383a29ee97a9306a309b3

Tx prefix hash: bfb37fe673b929a0e7d3d9ea382aa67ffe3d30ea299fa5108acc5f9128702a9c
Tx public key: 838d4479fca0bf7d9e71c1fd3c0ba712857691f09eb05eec3a81c2609746e34c
Timestamp: 1712246480 Timestamp [UCT]: 2024-04-04 16:01:20 Age [y:d:h:m:s]: 01:022:11:26:20
Block: 993248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277062 RingCT/type: yes/0
Extra: 01838d4479fca0bf7d9e71c1fd3c0ba712857691f09eb05eec3a81c2609746e34c02110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0ea52ac50bfe04f3a700ff340283765475d6e98bc86661820964fd0167f11a6 0.600000000000 1453634 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": 993258, "vin": [ { "gen": { "height": 993248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0ea52ac50bfe04f3a700ff340283765475d6e98bc86661820964fd0167f11a6" } } ], "extra": [ 1, 131, 141, 68, 121, 252, 160, 191, 125, 158, 113, 193, 253, 60, 11, 167, 18, 133, 118, 145, 240, 158, 176, 94, 236, 58, 129, 194, 96, 151, 70, 227, 76, 2, 17, 0, 0, 0, 12, 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