Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b441a44f3caf26dc740192235b52b1c7178d1fc96966735482750b2fbbf380b

Tx prefix hash: f5d456aaeb0e6c1ff9b094835c4d11b7fc250f1ccaa277edd1088f9771f45aa5
Tx public key: eac89dc2927532b807c53dc4e00898378404ffa49d252204efe41791aa35541e
Timestamp: 1649303063 Timestamp [UCT]: 2022-04-07 03:44:23 Age [y:d:h:m:s]: 02:271:18:30:53
Block: 474859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 714025 RingCT/type: yes/0
Extra: 01eac89dc2927532b807c53dc4e00898378404ffa49d252204efe41791aa35541e02110000000137cb3088000000000000000000

1 output(s) for total of 16.390615104000 dcy

stealth address amount amount idx
00: e0b92bd14c9dd34f03a9a6cec304bdf693a822da4ede0bb649f831b9931dced9 16.390615104000 894986 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": 474869, "vin": [ { "gen": { "height": 474859 } } ], "vout": [ { "amount": 16390615104, "target": { "key": "e0b92bd14c9dd34f03a9a6cec304bdf693a822da4ede0bb649f831b9931dced9" } } ], "extra": [ 1, 234, 200, 157, 194, 146, 117, 50, 184, 7, 197, 61, 196, 224, 8, 152, 55, 132, 4, 255, 164, 157, 37, 34, 4, 239, 228, 23, 145, 170, 53, 84, 30, 2, 17, 0, 0, 0, 1, 55, 203, 48, 136, 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