Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af70ad82747a411a04072a7f653b7d94db8ba1b8454f0fc1f48675468ec945c9

Tx prefix hash: bfbedf4a93712daaf9af0c45efefbf5f10328f138fbd786b76d61f61419ff79a
Tx public key: 095d4bda6a9b662c6d2f1cd8bc3b2415b06ae1c3e1f2fe10cba894754035ddcb
Timestamp: 1740301003 Timestamp [UCT]: 2025-02-23 08:56:43 Age [y:d:h:m:s]: 00:227:11:01:46
Block: 1225389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160276 RingCT/type: yes/0
Extra: 01095d4bda6a9b662c6d2f1cd8bc3b2415b06ae1c3e1f2fe10cba894754035ddcb021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 883e5771c2ee05edf9a64c28920e025b4da71412ecf4f4f2f23d12ec89e5dc4b 0.600000000000 1712254 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": 1225399, "vin": [ { "gen": { "height": 1225389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "883e5771c2ee05edf9a64c28920e025b4da71412ecf4f4f2f23d12ec89e5dc4b" } } ], "extra": [ 1, 9, 93, 75, 218, 106, 155, 102, 44, 109, 47, 28, 216, 188, 59, 36, 21, 176, 106, 225, 195, 225, 242, 254, 16, 203, 168, 148, 117, 64, 53, 221, 203, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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