Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8cf5a37bdfc4c63854fae2d642ea7e03aa0420d2f5dd858eb01f4b406b0537c

Tx prefix hash: ca8d6929a037da9bf0d21e3000f782c3788e4a9a2e55fcd73654793d569f6c1d
Tx public key: d1cd53828094f71fb039803c4f4ef1bbe71ed2694c1f1c59567d0af42556c9a6
Timestamp: 1707743926 Timestamp [UCT]: 2024-02-12 13:18:46 Age [y:d:h:m:s]: 00:248:13:39:21
Block: 955944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178058 RingCT/type: yes/0
Extra: 01d1cd53828094f71fb039803c4f4ef1bbe71ed2694c1f1c59567d0af42556c9a602110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81e1a188855aaba13ad32cfe5c2b9599183e0be1c2e4c59da05bea4343c9a1a9 0.600000000000 1415246 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": 955954, "vin": [ { "gen": { "height": 955944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81e1a188855aaba13ad32cfe5c2b9599183e0be1c2e4c59da05bea4343c9a1a9" } } ], "extra": [ 1, 209, 205, 83, 130, 128, 148, 247, 31, 176, 57, 128, 60, 79, 78, 241, 187, 231, 30, 210, 105, 76, 31, 28, 89, 86, 125, 10, 244, 37, 86, 201, 166, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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