Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4a65a61a84232ac1cb0f23b19efd3d03c7a1f78440377317addb09372adfe30

Tx prefix hash: 5e985d2b1140652bdb0308b4e74c052d0a42b1c40f3e85000c772c581c1b3906
Tx public key: ef753274492298d325da31b82fe28ce99a4d3e46a52eb0d54d5aa6d45b5499db
Timestamp: 1724404226 Timestamp [UCT]: 2024-08-23 09:10:26 Age [y:d:h:m:s]: 00:225:00:44:16
Block: 1094088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160674 RingCT/type: yes/0
Extra: 01ef753274492298d325da31b82fe28ce99a4d3e46a52eb0d54d5aa6d45b5499db02110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd298dfcdee63e114e9d4521230ad8e7bad5d82b3d09180a60ff501f72c88173 0.600000000000 1569159 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": 1094098, "vin": [ { "gen": { "height": 1094088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd298dfcdee63e114e9d4521230ad8e7bad5d82b3d09180a60ff501f72c88173" } } ], "extra": [ 1, 239, 117, 50, 116, 73, 34, 152, 211, 37, 218, 49, 184, 47, 226, 140, 233, 154, 77, 62, 70, 165, 46, 176, 213, 77, 90, 166, 212, 91, 84, 153, 219, 2, 17, 0, 0, 0, 12, 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