Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 839242cb02753ca513446a8683721d164bd0d3396d22f95b24d8616e2d061f0b

Tx prefix hash: 8bfff48d2125f6f09e7909d79e9094d5279e2a4ccd011519a5fcd5f8221d73a4
Tx public key: a13ad64b8c06c8adf03e9766d82065e32d18086565db5d181435b09f2d75b6b3
Timestamp: 1717221190 Timestamp [UCT]: 2024-06-01 05:53:10 Age [y:d:h:m:s]: 00:299:05:48:41
Block: 1034524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213841 RingCT/type: yes/0
Extra: 01a13ad64b8c06c8adf03e9766d82065e32d18086565db5d181435b09f2d75b6b30211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 614327778e3caa5e6ca8e41bb6040f5066a4885bb5b9b305469ef21683445ac7 0.600000000000 1503037 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": 1034534, "vin": [ { "gen": { "height": 1034524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "614327778e3caa5e6ca8e41bb6040f5066a4885bb5b9b305469ef21683445ac7" } } ], "extra": [ 1, 161, 58, 214, 75, 140, 6, 200, 173, 240, 62, 151, 102, 216, 32, 101, 227, 45, 24, 8, 101, 101, 219, 93, 24, 20, 53, 176, 159, 45, 117, 182, 179, 2, 17, 0, 0, 0, 2, 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