Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6641cf8888399a6846b11997437be4d5059da6f74839ad781848ab7068a199d3

Tx prefix hash: 664a192b8513c808908311fa03aa680ad2d23c3f478c818ab3521d80647453f3
Tx public key: 2bdea40051e561b457c9af64e883bb3841d3535c8d008ece47cfb8a60d25dc3c
Timestamp: 1639296359 Timestamp [UCT]: 2021-12-12 08:05:59 Age [y:d:h:m:s]: 02:341:15:55:25
Block: 393774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 762251 RingCT/type: yes/0
Extra: 012bdea40051e561b457c9af64e883bb3841d3535c8d008ece47cfb8a60d25dc3c021100000001408d5ef5000000000000000000

1 output(s) for total of 30.427315323000 dcy

stealth address amount amount idx
00: e13f0ef3ecf56d00c4f5e427e9f3bffa9481938cd88fa11895b7aed3870549aa 30.427315323000 791119 of 0

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": 393784, "vin": [ { "gen": { "height": 393774 } } ], "vout": [ { "amount": 30427315323, "target": { "key": "e13f0ef3ecf56d00c4f5e427e9f3bffa9481938cd88fa11895b7aed3870549aa" } } ], "extra": [ 1, 43, 222, 164, 0, 81, 229, 97, 180, 87, 201, 175, 100, 232, 131, 187, 56, 65, 211, 83, 92, 141, 0, 142, 206, 71, 207, 184, 166, 13, 37, 220, 60, 2, 17, 0, 0, 0, 1, 64, 141, 94, 245, 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