Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b5f5650e0a77b52872f8046b1bac6e9307a1f6db3d897bb0ed64d0ec26d4867

Tx prefix hash: 0ab1da75d010db5f2e4ca29ab9807fc8cde4c3cb2d20f2decf0c57dfea846da2
Tx public key: 2de76112633c67753b08dd73d4d12def9ed16208427179935e847d487e46d836
Timestamp: 1720464024 Timestamp [UCT]: 2024-07-08 18:40:24 Age [y:d:h:m:s]: 00:263:05:09:19
Block: 1061407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188046 RingCT/type: yes/0
Extra: 012de76112633c67753b08dd73d4d12def9ed16208427179935e847d487e46d836021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a37366266fa8cbc6fc41c7a4e6e261899c5c1ef60ecf62ea829c6c28a55c4ffb 0.600000000000 1531898 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": 1061417, "vin": [ { "gen": { "height": 1061407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a37366266fa8cbc6fc41c7a4e6e261899c5c1ef60ecf62ea829c6c28a55c4ffb" } } ], "extra": [ 1, 45, 231, 97, 18, 99, 60, 103, 117, 59, 8, 221, 115, 212, 209, 45, 239, 158, 209, 98, 8, 66, 113, 121, 147, 94, 132, 125, 72, 126, 70, 216, 54, 2, 17, 0, 0, 0, 7, 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