Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91f6157714be25fdfcd19ac11cc43ddb5f1b7fc4831ff7e8fe2926a23256da0d

Tx prefix hash: 89033724731b77e6f09016a9c78e3120e1dd5542a4a69b844d78825fc31cb542
Tx public key: 04fcecb5d6e1ca871d7b3bdefa530f7ff3d2b32952635311b466a669e446fbd1
Timestamp: 1673481063 Timestamp [UCT]: 2023-01-11 23:51:03 Age [y:d:h:m:s]: 02:096:05:42:31
Block: 672744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590462 RingCT/type: yes/0
Extra: 0104fcecb5d6e1ca871d7b3bdefa530f7ff3d2b32952635311b466a669e446fbd10211000000017e406890000000000000000000

1 output(s) for total of 3.621761201000 dcy

stealth address amount amount idx
00: 591fd2e548b3be55dcf708f1de0ee7d29e0d8a7aebcbbcdc2d3c361716cc85c7 3.621761201000 1114309 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": 672754, "vin": [ { "gen": { "height": 672744 } } ], "vout": [ { "amount": 3621761201, "target": { "key": "591fd2e548b3be55dcf708f1de0ee7d29e0d8a7aebcbbcdc2d3c361716cc85c7" } } ], "extra": [ 1, 4, 252, 236, 181, 214, 225, 202, 135, 29, 123, 59, 222, 250, 83, 15, 127, 243, 210, 179, 41, 82, 99, 83, 17, 180, 102, 166, 105, 228, 70, 251, 209, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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