Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1a61c53f9605950451861ceb5a2564b5323564308ad78a75364f44957e1552e

Tx prefix hash: 77de73c4fc749843c28099eb5ec2e7136ae3ae4b5ebc1e8b793d68c4bcd9e4fb
Tx public key: f0d4079eb15b73999fbc7efb55a77b6c3119e8fb354773659ca4150a52c5139a
Timestamp: 1714221718 Timestamp [UCT]: 2024-04-27 12:41:58 Age [y:d:h:m:s]: 01:014:09:13:38
Block: 1009644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271225 RingCT/type: yes/0
Extra: 01f0d4079eb15b73999fbc7efb55a77b6c3119e8fb354773659ca4150a52c5139a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99e5f36fe257ec2dbc52213fa967f59076d32e027c2db1a18cc98f299f418b74 0.600000000000 1471376 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": 1009654, "vin": [ { "gen": { "height": 1009644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99e5f36fe257ec2dbc52213fa967f59076d32e027c2db1a18cc98f299f418b74" } } ], "extra": [ 1, 240, 212, 7, 158, 177, 91, 115, 153, 159, 188, 126, 251, 85, 167, 123, 108, 49, 25, 232, 251, 53, 71, 115, 101, 156, 164, 21, 10, 82, 197, 19, 154, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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