Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48fed47b52a98febca382bf6769e75a1dc1f9798b07646ee9b09f9d98f18f804

Tx prefix hash: 0ebf369d15d41b7c00eca759e0c5421b094fd3543991404238ad52d696dcf11e
Tx public key: 1a97264862c8de166c66118933a1ac82b292b3c0fb8fe233c3ce1bce529dd2f8
Timestamp: 1711340252 Timestamp [UCT]: 2024-03-25 04:17:32 Age [y:d:h:m:s]: 01:230:18:47:29
Block: 985780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423618 RingCT/type: yes/0
Extra: 011a97264862c8de166c66118933a1ac82b292b3c0fb8fe233c3ce1bce529dd2f80211000000020424019c000000000000000000

1 output(s) for total of 0.600060000000 dcy

stealth address amount amount idx
00: 45ccf9c57a6101f54be4d51cdf4898934fda60aa7bbb9d03976720378f8f9457 0.600060000000 1445997 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": 985790, "vin": [ { "gen": { "height": 985780 } } ], "vout": [ { "amount": 600060000, "target": { "key": "45ccf9c57a6101f54be4d51cdf4898934fda60aa7bbb9d03976720378f8f9457" } } ], "extra": [ 1, 26, 151, 38, 72, 98, 200, 222, 22, 108, 102, 17, 137, 51, 161, 172, 130, 178, 146, 179, 192, 251, 143, 226, 51, 195, 206, 27, 206, 82, 157, 210, 248, 2, 17, 0, 0, 0, 2, 4, 36, 1, 156, 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