Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9b43e86c5279ca5bab5d3f3862679b0ea8b27be8ec6eef0324c99e3c048ebb4

Tx prefix hash: 227ba33e9239f598e6a4c333c0cc33347cc51c26361d9cc6ea6a66de2fe74e04
Tx public key: 9db9207dcd5fc8a6ceecd9e001852aeba9b9df555f15a20e8f9f134b3fe8e57b
Timestamp: 1705690093 Timestamp [UCT]: 2024-01-19 18:48:13 Age [y:d:h:m:s]: 01:084:03:51:58
Block: 938890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321253 RingCT/type: yes/0
Extra: 019db9207dcd5fc8a6ceecd9e001852aeba9b9df555f15a20e8f9f134b3fe8e57b0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9eafef2e3ea1e493bdc73b70fc6a0d627f6d67b9cf7cfd2b28628bf9bba9d1c 0.600000000000 1396972 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": 938900, "vin": [ { "gen": { "height": 938890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9eafef2e3ea1e493bdc73b70fc6a0d627f6d67b9cf7cfd2b28628bf9bba9d1c" } } ], "extra": [ 1, 157, 185, 32, 125, 205, 95, 200, 166, 206, 236, 217, 224, 1, 133, 42, 235, 169, 185, 223, 85, 95, 21, 162, 14, 143, 159, 19, 75, 63, 232, 229, 123, 2, 17, 0, 0, 0, 6, 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