Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d6a677cfaf1951356c905dd2c1aa9c43f17d4e57cc5cd3ab16ef67ebaa3a2aa

Tx prefix hash: a7efa7662abaf60d4ac0ff2eca5b6ca0c89b9c82a521281c6459a393bc884a48
Tx public key: 1addf44775921166ed484fd0f222a528b05043e02fa81a3ca69988732fc3b6fc
Timestamp: 1694866687 Timestamp [UCT]: 2023-09-16 12:18:07 Age [y:d:h:m:s]: 01:201:21:42:30
Block: 849379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405386 RingCT/type: yes/0
Extra: 011addf44775921166ed484fd0f222a528b05043e02fa81a3ca69988732fc3b6fc02110000000ae6d27f9c000000000000000000

1 output(s) for total of 0.941141310000 dcy

stealth address amount amount idx
00: f4eaba6305dfb8a44aba82b244c8be2acee08579530ae7d29b15e5896a749a56 0.941141310000 1303039 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": 849389, "vin": [ { "gen": { "height": 849379 } } ], "vout": [ { "amount": 941141310, "target": { "key": "f4eaba6305dfb8a44aba82b244c8be2acee08579530ae7d29b15e5896a749a56" } } ], "extra": [ 1, 26, 221, 244, 71, 117, 146, 17, 102, 237, 72, 79, 208, 242, 34, 165, 40, 176, 80, 67, 224, 47, 168, 26, 60, 166, 153, 136, 115, 47, 195, 182, 252, 2, 17, 0, 0, 0, 10, 230, 210, 127, 156, 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