Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b1a25ccc91e56a80c7a2c8e51cf7e47c93f859d568cb01235829a50343bf01a

Tx prefix hash: 66737746806af8da2ad77c49ee6ce2ff387f4bb25a0ecfc781226d14ab31dd98
Tx public key: 72d671ef4853afa5c51149ba3e8b5ef0a04a9b53c9ba2b7c1e2654fa6891e8c7
Timestamp: 1700110828 Timestamp [UCT]: 2023-11-16 05:00:28 Age [y:d:h:m:s]: 01:066:20:26:37
Block: 892661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309148 RingCT/type: yes/0
Extra: 0172d671ef4853afa5c51149ba3e8b5ef0a04a9b53c9ba2b7c1e2654fa6891e8c702110000000133af99f4000000000000000000

1 output(s) for total of 0.676462210000 dcy

stealth address amount amount idx
00: 0319474896d650aa27ad0a1f0e277d1d38e3190342e53f8351ca5203fc09de49 0.676462210000 1348784 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": 892671, "vin": [ { "gen": { "height": 892661 } } ], "vout": [ { "amount": 676462210, "target": { "key": "0319474896d650aa27ad0a1f0e277d1d38e3190342e53f8351ca5203fc09de49" } } ], "extra": [ 1, 114, 214, 113, 239, 72, 83, 175, 165, 197, 17, 73, 186, 62, 139, 94, 240, 160, 74, 155, 83, 201, 186, 43, 124, 30, 38, 84, 250, 104, 145, 232, 199, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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