Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 068616cb0849b624fdf9c2f782a098f2edcb9d0a0c08c7aee12b238ddea0a542

Tx prefix hash: 4028bdeabb6855195795444a71d8fb9c867881ae04c9ccaf1511b917d81e9219
Tx public key: 4ad530b02c8c7de5ff59da80ed0d4017d3566a5666cc8a22086d7f648650c5fa
Timestamp: 1702305451 Timestamp [UCT]: 2023-12-11 14:37:31 Age [y:d:h:m:s]: 01:156:20:02:38
Block: 910857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373250 RingCT/type: yes/0
Extra: 014ad530b02c8c7de5ff59da80ed0d4017d3566a5666cc8a22086d7f648650c5fa021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f54c46cb3f6b9533f037beacd168efdb06fc5014a97d520d12c462bd4129453 0.600000000000 1368032 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": 910867, "vin": [ { "gen": { "height": 910857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f54c46cb3f6b9533f037beacd168efdb06fc5014a97d520d12c462bd4129453" } } ], "extra": [ 1, 74, 213, 48, 176, 44, 140, 125, 229, 255, 89, 218, 128, 237, 13, 64, 23, 211, 86, 106, 86, 102, 204, 138, 34, 8, 109, 127, 100, 134, 80, 197, 250, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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