Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9c1c7e7bdbdd3f28f90a3f3379fcd66d50422e6bdcd7467e74100b3826ce0ba

Tx prefix hash: 4b288f5a9cc6ae30f170e24f8ba4cbf2bd8acb3f4c6779bfc628eb4e83accbba
Tx public key: 8bf9eaf3a850e15f16866315479fc5e0e842c31f341ffefc7f86d4807887d98e
Timestamp: 1574653397 Timestamp [UCT]: 2019-11-25 03:43:17 Age [y:d:h:m:s]: 05:035:20:21:38
Block: 16872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168479 RingCT/type: yes/0
Extra: 018bf9eaf3a850e15f16866315479fc5e0e842c31f341ffefc7f86d4807887d98e021100000001f95225a5000000000000000000

1 output(s) for total of 539.631063404000 dcy

stealth address amount amount idx
00: 8e5c8ab1eb08c2a64a8f3df7570afe7c3223d8c4bba1af742fd562ac68a8d5c3 539.631063404000 23966 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": 16882, "vin": [ { "gen": { "height": 16872 } } ], "vout": [ { "amount": 539631063404, "target": { "key": "8e5c8ab1eb08c2a64a8f3df7570afe7c3223d8c4bba1af742fd562ac68a8d5c3" } } ], "extra": [ 1, 139, 249, 234, 243, 168, 80, 225, 95, 22, 134, 99, 21, 71, 159, 197, 224, 232, 66, 195, 31, 52, 31, 254, 252, 127, 134, 212, 128, 120, 135, 217, 142, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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