Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82c458ad7a53365061a431feb4de44b03f09c973db4c7529cb7e730cfe25a453

Tx prefix hash: 7653a1572ead1e7d29568b66a2413cebaf862c9efc946ab576ae9f855e9c347a
Tx public key: cf0e757d795f00513c28da98d43a8d53410183ad65078794f9c85f1c782c1a52
Timestamp: 1720696278 Timestamp [UCT]: 2024-07-11 11:11:18 Age [y:d:h:m:s]: 01:126:13:21:33
Block: 1063336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348970 RingCT/type: yes/0
Extra: 01cf0e757d795f00513c28da98d43a8d53410183ad65078794f9c85f1c782c1a5202110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d305fbe18a710d76bf86e00d8b21e0e9174bd8bf9bcc0a16ef1f15f0879b00f5 0.600000000000 1533851 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": 1063346, "vin": [ { "gen": { "height": 1063336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d305fbe18a710d76bf86e00d8b21e0e9174bd8bf9bcc0a16ef1f15f0879b00f5" } } ], "extra": [ 1, 207, 14, 117, 125, 121, 95, 0, 81, 60, 40, 218, 152, 212, 58, 141, 83, 65, 1, 131, 173, 101, 7, 135, 148, 249, 200, 95, 28, 120, 44, 26, 82, 2, 17, 0, 0, 0, 11, 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