Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f8b2bb8e8dfac4585c77923383d194b78af2b6fb40925f935861e3173e35021

Tx prefix hash: 69b89617e7f2676bbf5807f8bd745b6377dac8c9f12853d64c92421f7fc346d7
Tx public key: c4b23843e96881547d2cb6eda6606674834f2ca80eed4c9d2d411814cc32a260
Timestamp: 1722480502 Timestamp [UCT]: 2024-08-01 02:48:22 Age [y:d:h:m:s]: 00:248:08:13:37
Block: 1078121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177389 RingCT/type: yes/0
Extra: 01c4b23843e96881547d2cb6eda6606674834f2ca80eed4c9d2d411814cc32a26002110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 144bc36f296ec6b5d99616d466fe082b65ea7d4fb45ce9ea35b5dc8971b1b6d1 0.600000000000 1550684 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": 1078131, "vin": [ { "gen": { "height": 1078121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "144bc36f296ec6b5d99616d466fe082b65ea7d4fb45ce9ea35b5dc8971b1b6d1" } } ], "extra": [ 1, 196, 178, 56, 67, 233, 104, 129, 84, 125, 44, 182, 237, 166, 96, 102, 116, 131, 79, 44, 168, 14, 237, 76, 157, 45, 65, 24, 20, 204, 50, 162, 96, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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