Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1e77484b58adc23c4506de7c1c26561258638504d0e8ef5c0ac2725e9b848b9

Tx prefix hash: f4f561f84720c1ef207695d23acea8bb21266498d409aa49c782b9e239d450cc
Tx public key: 7430d3a60c092ffcdd9de1ceecc242d7042a5fb60db88f8779ca55b8269df213
Timestamp: 1722546540 Timestamp [UCT]: 2024-08-01 21:09:00 Age [y:d:h:m:s]: 00:320:03:33:14
Block: 1078666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228636 RingCT/type: yes/0
Extra: 017430d3a60c092ffcdd9de1ceecc242d7042a5fb60db88f8779ca55b8269df213021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cb97d2b5c481db8738961da9342a0e837f1d66d94d9c4a1ce881bba205be496 0.600000000000 1551293 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": 1078676, "vin": [ { "gen": { "height": 1078666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cb97d2b5c481db8738961da9342a0e837f1d66d94d9c4a1ce881bba205be496" } } ], "extra": [ 1, 116, 48, 211, 166, 12, 9, 47, 252, 221, 157, 225, 206, 236, 194, 66, 215, 4, 42, 95, 182, 13, 184, 143, 135, 121, 202, 85, 184, 38, 157, 242, 19, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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