Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3507080ed0c5f19f656425c5698d9b0d13ec4737d2265e8c5954fe7f88047466

Tx prefix hash: be401f8b31356a155d885b047281961fa24b6321285c11ceaf962b66bf53f55d
Tx public key: bcb5dfa0fe110f61c8e8c637768288b4adb5f3f7b5a4f7432a9c112bfbc66a31
Timestamp: 1705933450 Timestamp [UCT]: 2024-01-22 14:24:10 Age [y:d:h:m:s]: 00:354:12:34:27
Block: 940902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253835 RingCT/type: yes/0
Extra: 01bcb5dfa0fe110f61c8e8c637768288b4adb5f3f7b5a4f7432a9c112bfbc66a3102110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47cf32df3905052958c6236fdbed6eb191cd6b2951a08718e471cb0e82c9c679 0.600000000000 1399042 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": 940912, "vin": [ { "gen": { "height": 940902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47cf32df3905052958c6236fdbed6eb191cd6b2951a08718e471cb0e82c9c679" } } ], "extra": [ 1, 188, 181, 223, 160, 254, 17, 15, 97, 200, 232, 198, 55, 118, 130, 136, 180, 173, 181, 243, 247, 181, 164, 247, 67, 42, 156, 17, 43, 251, 198, 106, 49, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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