Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc7b9758d13a3a1e60e693b78de3fee47670b429b9be04ca5f7ffcc0a8019872

Tx prefix hash: 7344c808efc18da482578f9b309792cdd813f694baf825e389c95507a73d1bcd
Tx public key: 41f0086a4fc6b674ca8000d9e6cc55b19277ac4eefcdb9c2cab6531f13fba0d3
Timestamp: 1711112223 Timestamp [UCT]: 2024-03-22 12:57:03 Age [y:d:h:m:s]: 00:275:16:51:34
Block: 983894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197371 RingCT/type: yes/0
Extra: 0141f0086a4fc6b674ca8000d9e6cc55b19277ac4eefcdb9c2cab6531f13fba0d30211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e911d04c5634804619d2361fce210c897f4bd046fa22b53c365a90196588cbd2 0.600000000000 1444047 of 15

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": 983904, "vin": [ { "gen": { "height": 983894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e911d04c5634804619d2361fce210c897f4bd046fa22b53c365a90196588cbd2" } } ], "extra": [ 1, 65, 240, 8, 106, 79, 198, 182, 116, 202, 128, 0, 217, 230, 204, 85, 177, 146, 119, 172, 78, 239, 205, 185, 194, 202, 182, 83, 31, 19, 251, 160, 211, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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