Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53017a72f87328784fad1addffecb670e1d1dd482a0805a4c3c4a9151da5c618

Tx prefix hash: fdca3687f3d1129cbd345c9ea00040e74cb0e42ddb8c683a324695759691e9d3
Tx public key: 6d75a29a1b265981dc57d3ce30fcfeceb93d2291158b250b30d0d64ed8e822c6
Timestamp: 1720850623 Timestamp [UCT]: 2024-07-13 06:03:43 Age [y:d:h:m:s]: 00:337:16:52:27
Block: 1064624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241211 RingCT/type: yes/0
Extra: 016d75a29a1b265981dc57d3ce30fcfeceb93d2291158b250b30d0d64ed8e822c602110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15a18ba5aa3fd41b69201620957f8d8c31bbd2aec0103aff595fa68a463aca53 0.600000000000 1535155 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": 1064634, "vin": [ { "gen": { "height": 1064624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15a18ba5aa3fd41b69201620957f8d8c31bbd2aec0103aff595fa68a463aca53" } } ], "extra": [ 1, 109, 117, 162, 154, 27, 38, 89, 129, 220, 87, 211, 206, 48, 252, 254, 206, 185, 61, 34, 145, 21, 139, 37, 11, 48, 208, 214, 78, 216, 232, 34, 198, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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