Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfba84476fa0ff182280d1462bdd3b1379909e3669a1c54261b38cebfad997e2

Tx prefix hash: d7ecb7f6938199a09068f17c7b5df5171dc0f033605b45c75d546b69287b2883
Tx public key: c611033f41ee02ae9b242e7285b78779436330c21710f7cc4f0e382ebf310700
Timestamp: 1710304087 Timestamp [UCT]: 2024-03-13 04:28:07 Age [y:d:h:m:s]: 00:302:01:56:58
Block: 977185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216227 RingCT/type: yes/0
Extra: 01c611033f41ee02ae9b242e7285b78779436330c21710f7cc4f0e382ebf31070002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4f45de0f3c4762d2092904e94d52dd5e3d4b2cc6ec100d2d11547df8f695846 0.600000000000 1437186 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": 977195, "vin": [ { "gen": { "height": 977185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4f45de0f3c4762d2092904e94d52dd5e3d4b2cc6ec100d2d11547df8f695846" } } ], "extra": [ 1, 198, 17, 3, 63, 65, 238, 2, 174, 155, 36, 46, 114, 133, 183, 135, 121, 67, 99, 48, 194, 23, 16, 247, 204, 79, 14, 56, 46, 191, 49, 7, 0, 2, 17, 0, 0, 0, 2, 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