Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a49ba04962fe83dccacc35d12bf9cbeb05ad00ea19fbc2a5f4a7840b382b870e

Tx prefix hash: baaee81986c9ed4ef03f9372abd96d9ae7fcb7fcbc55062f31447b07a1c73c06
Tx public key: 36336e4a1cc47ad721f2b6fed1d9358dcea9366c0f483ef14c94cbdb05ad2329
Timestamp: 1714552075 Timestamp [UCT]: 2024-05-01 08:27:55 Age [y:d:h:m:s]: 00:303:01:42:30
Block: 1012396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216606 RingCT/type: yes/0
Extra: 0136336e4a1cc47ad721f2b6fed1d9358dcea9366c0f483ef14c94cbdb05ad23290211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8300b1f2aff2cb3d4f0d6af1ce7294815c3c083eb4124eaa95ddec5ed08d369 0.600000000000 1474904 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": 1012406, "vin": [ { "gen": { "height": 1012396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8300b1f2aff2cb3d4f0d6af1ce7294815c3c083eb4124eaa95ddec5ed08d369" } } ], "extra": [ 1, 54, 51, 110, 74, 28, 196, 122, 215, 33, 242, 182, 254, 209, 217, 53, 141, 206, 169, 54, 108, 15, 72, 62, 241, 76, 148, 203, 219, 5, 173, 35, 41, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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