Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa66736e04b6342a25d3a178f0e222359a377078d781dac660d64c6e1fdf4014

Tx prefix hash: f518992f7f66cb403e99dca308cd2544e328bf4576e8c6b4aa5b19ebfe7796c5
Tx public key: 8ed8bc30340ebe41fc2d473e4e85ed1d420096a58afaef102d05b4367b5c0a64
Timestamp: 1735351639 Timestamp [UCT]: 2024-12-28 02:07:19 Age [y:d:h:m:s]: 00:100:05:00:31
Block: 1184693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71412 RingCT/type: yes/0
Extra: 018ed8bc30340ebe41fc2d473e4e85ed1d420096a58afaef102d05b4367b5c0a640211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 106f3b1b1e79e2d7896c6cc3ef64a046071c6f08ed2f50c672b4e493908658db 0.600000000000 1671152 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": 1184703, "vin": [ { "gen": { "height": 1184693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "106f3b1b1e79e2d7896c6cc3ef64a046071c6f08ed2f50c672b4e493908658db" } } ], "extra": [ 1, 142, 216, 188, 48, 52, 14, 190, 65, 252, 45, 71, 62, 78, 133, 237, 29, 66, 0, 150, 165, 138, 250, 239, 16, 45, 5, 180, 54, 123, 92, 10, 100, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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