Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be8d088fbe3590bcb7f71fff3442705338ae5e7b4e849c651e681e6fa889727b

Tx prefix hash: fa5ac1466d07478dc55dfc44b90c30e6fede3bab301d6369b6ea9e122a05a178
Tx public key: c981973f081ff186df8da1684dc147e3a999994f2f8329a9506c19cec4626c59
Timestamp: 1705523513 Timestamp [UCT]: 2024-01-17 20:31:53 Age [y:d:h:m:s]: 00:288:04:09:39
Block: 937516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206367 RingCT/type: yes/0
Extra: 01c981973f081ff186df8da1684dc147e3a999994f2f8329a9506c19cec4626c5902110000000f59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea571b2c1bbd6cc8c49dcd0b0d2c73ef20b5233e8fb6cab088e5720adc4d1bf4 0.600000000000 1395572 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": 937526, "vin": [ { "gen": { "height": 937516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea571b2c1bbd6cc8c49dcd0b0d2c73ef20b5233e8fb6cab088e5720adc4d1bf4" } } ], "extra": [ 1, 201, 129, 151, 63, 8, 31, 241, 134, 223, 141, 161, 104, 77, 193, 71, 227, 169, 153, 153, 79, 47, 131, 41, 169, 80, 108, 25, 206, 196, 98, 108, 89, 2, 17, 0, 0, 0, 15, 89, 218, 211, 245, 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