Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 933fbedab987ab939673c3a1bbdb5ee1fb852fedb7f570998d0980b652ad9c7b

Tx prefix hash: 9a07701daf2d93f87464277e23418cb1914245e22597c1813f0fb57a52a69526
Tx public key: 104ef6f925c5a016de893a00f695474bc356591c4ceeaed7604a2ee6f5e44d9c
Timestamp: 1699353964 Timestamp [UCT]: 2023-11-07 10:46:04 Age [y:d:h:m:s]: 02:002:01:36:46
Block: 886393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521247 RingCT/type: yes/0
Extra: 01104ef6f925c5a016de893a00f695474bc356591c4ceeaed7604a2ee6f5e44d9c02110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.709597432000 dcy

stealth address amount amount idx
00: e496015767fa35fda52c641b22b491da9a166a4b0af1e02467b76fed3454a70c 0.709597432000 1342208 of 0

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": 886403, "vin": [ { "gen": { "height": 886393 } } ], "vout": [ { "amount": 709597432, "target": { "key": "e496015767fa35fda52c641b22b491da9a166a4b0af1e02467b76fed3454a70c" } } ], "extra": [ 1, 16, 78, 246, 249, 37, 197, 160, 22, 222, 137, 58, 0, 246, 149, 71, 75, 195, 86, 89, 28, 76, 238, 174, 215, 96, 74, 46, 230, 245, 228, 77, 156, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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