Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f75bafe5c0a84fd17ad72569b54c043d61073bfa84fb95d8d49c96f5daaecdc4

Tx prefix hash: d0ede50eff4d64412214abfa7d9aa2fef870dc8f75b1cb38264004dcfde7b245
Tx public key: d040b8ee1da383d4e581cd75963cc656b4bdc573173c3ef37ec4259c7c04bf68
Timestamp: 1709901136 Timestamp [UCT]: 2024-03-08 12:32:16 Age [y:d:h:m:s]: 01:067:20:50:49
Block: 973845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309514 RingCT/type: yes/0
Extra: 01d040b8ee1da383d4e581cd75963cc656b4bdc573173c3ef37ec4259c7c04bf680211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e11258cf0d9af81c193c3e4a323fdd739d1ba46532eae3cd517b764ecd255d67 0.600000000000 1433786 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": 973855, "vin": [ { "gen": { "height": 973845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e11258cf0d9af81c193c3e4a323fdd739d1ba46532eae3cd517b764ecd255d67" } } ], "extra": [ 1, 208, 64, 184, 238, 29, 163, 131, 212, 229, 129, 205, 117, 150, 60, 198, 86, 180, 189, 197, 115, 23, 60, 62, 243, 126, 196, 37, 156, 124, 4, 191, 104, 2, 17, 0, 0, 0, 5, 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