Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5f589e96acd615b4410034b65425bed3e21b9d53be84200e09965f4f3395c03

Tx prefix hash: 9869fd0e30ac3b334e7e37b1925f80c1bacd158a9e7ab05913257330e3a530d4
Tx public key: 0ebe72a88d9d8a2080f730967ae96b5a141bdfbfb6bc643773d89462548bf4d8
Timestamp: 1721037509 Timestamp [UCT]: 2024-07-15 09:58:29 Age [y:d:h:m:s]: 01:114:13:18:00
Block: 1066169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340356 RingCT/type: yes/0
Extra: 010ebe72a88d9d8a2080f730967ae96b5a141bdfbfb6bc643773d89462548bf4d802110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e06a78e620fe9bc39b0e64fdf1745bb69a64aa8e618bce6df20460b3906ce74c 0.600000000000 1536742 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": 1066179, "vin": [ { "gen": { "height": 1066169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e06a78e620fe9bc39b0e64fdf1745bb69a64aa8e618bce6df20460b3906ce74c" } } ], "extra": [ 1, 14, 190, 114, 168, 141, 157, 138, 32, 128, 247, 48, 150, 122, 233, 107, 90, 20, 27, 223, 191, 182, 188, 100, 55, 115, 216, 148, 98, 84, 139, 244, 216, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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