Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8a8b83dbe61565956ed419e0e174c8722399bbae0a53002ade853d0ea5bb1d5

Tx prefix hash: 9e328d701b71147c87561b40a3563be48b1ad98950c438e7dea1499f40603891
Tx public key: bc5b62f5efc5898db48397a547d0a88f73d4a52073d28b66216b6589b7ab36f8
Timestamp: 1703513189 Timestamp [UCT]: 2023-12-25 14:06:29 Age [y:d:h:m:s]: 01:102:06:17:51
Block: 920878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334191 RingCT/type: yes/0
Extra: 01bc5b62f5efc5898db48397a547d0a88f73d4a52073d28b66216b6589b7ab36f802110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27cecb285022b6f8a3fc736c8ae3a41fda8878bce3b2e1e62ed1729eb70d1c22 0.600000000000 1378562 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": 920888, "vin": [ { "gen": { "height": 920878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27cecb285022b6f8a3fc736c8ae3a41fda8878bce3b2e1e62ed1729eb70d1c22" } } ], "extra": [ 1, 188, 91, 98, 245, 239, 197, 137, 141, 180, 131, 151, 165, 71, 208, 168, 143, 115, 212, 165, 32, 115, 210, 139, 102, 33, 107, 101, 137, 183, 171, 54, 248, 2, 17, 0, 0, 0, 7, 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