Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ed36b940f68dcf76616fc1f746eb9a36d4a8ac793fef16d61e6db4ea3d16446

Tx prefix hash: cf68ba9e3eb490409276a2152ca71959b3c4263c273060e9e4103d3894992c9b
Tx public key: 0093d74774af1458b7177c0f823b07e4487bd7a29d9504efdf619ea524eeeced
Timestamp: 1728525713 Timestamp [UCT]: 2024-10-10 02:01:53 Age [y:d:h:m:s]: 00:178:22:43:40
Block: 1128234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127675 RingCT/type: yes/0
Extra: 010093d74774af1458b7177c0f823b07e4487bd7a29d9504efdf619ea524eeeced021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2416108ef29d679bfea9b665ae0794f02b5eb0e5584b96cb497ad019c5b0a3bb 0.600000000000 1611051 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": 1128244, "vin": [ { "gen": { "height": 1128234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2416108ef29d679bfea9b665ae0794f02b5eb0e5584b96cb497ad019c5b0a3bb" } } ], "extra": [ 1, 0, 147, 215, 71, 116, 175, 20, 88, 183, 23, 124, 15, 130, 59, 7, 228, 72, 123, 215, 162, 157, 149, 4, 239, 223, 97, 158, 165, 36, 238, 236, 237, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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