Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bdef05428eab8002f113e0efe80c0832150c9de7d298d7e764f61719352e3d1

Tx prefix hash: ab0e97abcc846d1cd8b0874cf0a248db9c4da3cbff0e7b8b4df0921ea3cbd63e
Tx public key: 55922b7d1e1b90ebda7f90f8c234ae7c2434a29fca09b2c0e70f60ee641d4566
Timestamp: 1745796618 Timestamp [UCT]: 2025-04-27 23:30:18 Age [y:d:h:m:s]: 00:205:01:06:01
Block: 1270915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144258 RingCT/type: yes/0
Extra: 0155922b7d1e1b90ebda7f90f8c234ae7c2434a29fca09b2c0e70f60ee641d45660211000000069f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff9b3cf24c19cf1227fecd299e0d184c32ed15b0e21bc2ead80b151f00ce5b29 0.600000000000 1758160 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": 1270925, "vin": [ { "gen": { "height": 1270915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff9b3cf24c19cf1227fecd299e0d184c32ed15b0e21bc2ead80b151f00ce5b29" } } ], "extra": [ 1, 85, 146, 43, 125, 30, 27, 144, 235, 218, 127, 144, 248, 194, 52, 174, 124, 36, 52, 162, 159, 202, 9, 178, 192, 231, 15, 96, 238, 100, 29, 69, 102, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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