Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32f2b2f70679320087d2b087ee09cd1ebaac73f2859d01dee33fda85a85b2eb0

Tx prefix hash: 4f688d2259a2fb6870b748448214be1d7bbcbe32b46b5dc7be0c188b93ad6723
Tx public key: 82fb6ee2b27a7835f33aef76bd10c97a6bb3705c685e8848ae79e0c261bff543
Timestamp: 1725225805 Timestamp [UCT]: 2024-09-01 21:23:25 Age [y:d:h:m:s]: 01:059:18:37:51
Block: 1100884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301149 RingCT/type: yes/0
Extra: 0182fb6ee2b27a7835f33aef76bd10c97a6bb3705c685e8848ae79e0c261bff54302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc5f6a5b96436bff59ec3cc37d3677b7b80a53ddd10dd028d672c38711bf1466 0.600000000000 1576865 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": 1100894, "vin": [ { "gen": { "height": 1100884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc5f6a5b96436bff59ec3cc37d3677b7b80a53ddd10dd028d672c38711bf1466" } } ], "extra": [ 1, 130, 251, 110, 226, 178, 122, 120, 53, 243, 58, 239, 118, 189, 16, 201, 122, 107, 179, 112, 92, 104, 94, 136, 72, 174, 121, 224, 194, 97, 191, 245, 67, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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