Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5606a8cfbe15d8d11112618be39fd652bb6dce068d39f676f5c200a32db8609d

Tx prefix hash: f382746d3795d2a3c8bf837a77cb9bf83984ee1a10c21ef0e2ea2b66592777b5
Tx public key: f56da37ce14e0344a8b58ac1cc0af8e250537cbaa4612adf8f0b6bc91f4c7142
Timestamp: 1647055117 Timestamp [UCT]: 2022-03-12 03:18:37 Age [y:d:h:m:s]: 03:238:09:50:50
Block: 456544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 948258 RingCT/type: yes/0
Extra: 01f56da37ce14e0344a8b58ac1cc0af8e250537cbaa4612adf8f0b6bc91f4c714202110000000ec9067537000000000000000000

1 output(s) for total of 18.848659836000 dcy

stealth address amount amount idx
00: 68fc99b52a80a24d96ab219d1dc9b38b5f483ef0efa98304cc44c42751f6cda9 18.848659836000 872623 of 0

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": 456554, "vin": [ { "gen": { "height": 456544 } } ], "vout": [ { "amount": 18848659836, "target": { "key": "68fc99b52a80a24d96ab219d1dc9b38b5f483ef0efa98304cc44c42751f6cda9" } } ], "extra": [ 1, 245, 109, 163, 124, 225, 78, 3, 68, 168, 181, 138, 193, 204, 10, 248, 226, 80, 83, 124, 186, 164, 97, 42, 223, 143, 11, 107, 201, 31, 76, 113, 66, 2, 17, 0, 0, 0, 14, 201, 6, 117, 55, 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