Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a2cf6ed1f322051a527fec6d7a88ee9341f46663d689d358a3f7d2dfd039a11

Tx prefix hash: 08aded754b6ef78ddac0dfbede2b8478fa969f2bde7dce0f250b526350748713
Tx public key: dc9069d679d8c0be909d63fb4d481ef566dc193e07575a5ccf8007867b362eac
Timestamp: 1704069057 Timestamp [UCT]: 2024-01-01 00:30:57 Age [y:d:h:m:s]: 01:144:09:47:30
Block: 925477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364355 RingCT/type: yes/0
Extra: 01dc9069d679d8c0be909d63fb4d481ef566dc193e07575a5ccf8007867b362eac02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a1673e001e1f06ad6b93182dfc6e5fc52bd00207bf64d8215f34e7936660a16 0.600000000000 1383241 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": 925487, "vin": [ { "gen": { "height": 925477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a1673e001e1f06ad6b93182dfc6e5fc52bd00207bf64d8215f34e7936660a16" } } ], "extra": [ 1, 220, 144, 105, 214, 121, 216, 192, 190, 144, 157, 99, 251, 77, 72, 30, 245, 102, 220, 25, 62, 7, 87, 90, 92, 207, 128, 7, 134, 123, 54, 46, 172, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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