Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aec78869183f3c982a1bb98a709e8d379cb95e311b829546d9b975314a82bd08

Tx prefix hash: 3f764d94a7207d537fb71db88048449f16acb8a45a65e8781e44a6667ff33818
Tx public key: c12b7c5524619e2f85e6f09f9d1d20d626e3850e796c232cba0cdaa182df4321
Timestamp: 1742390770 Timestamp [UCT]: 2025-03-19 13:26:10 Age [y:d:h:m:s]: 00:066:11:04:01
Block: 1242733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47525 RingCT/type: yes/0
Extra: 01c12b7c5524619e2f85e6f09f9d1d20d626e3850e796c232cba0cdaa182df43210211000000041db82ba9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fcf2a05057f210b07dd0901bd1a83bc48151479f5fdbd93185e30dfdd36fe32 0.600000000000 1729708 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": 1242743, "vin": [ { "gen": { "height": 1242733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fcf2a05057f210b07dd0901bd1a83bc48151479f5fdbd93185e30dfdd36fe32" } } ], "extra": [ 1, 193, 43, 124, 85, 36, 97, 158, 47, 133, 230, 240, 159, 157, 29, 32, 214, 38, 227, 133, 14, 121, 108, 35, 44, 186, 12, 218, 161, 130, 223, 67, 33, 2, 17, 0, 0, 0, 4, 29, 184, 43, 169, 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