Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d9a69ad1e161f18884abe706a10ed80b658372bfd94e65be115f152b31ca25f

Tx prefix hash: a43d2055570ccdbd6316ec8561c79337b8cbb2bcacf8c0e49a03f533bc13c3d0
Tx public key: 8b16e522052ca1cb703ea72b258a5a4718b34d5d1ea9c333d7a6778cead32cb9
Timestamp: 1728044202 Timestamp [UCT]: 2024-10-04 12:16:42 Age [y:d:h:m:s]: 00:110:05:53:05
Block: 1124250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78770 RingCT/type: yes/0
Extra: 018b16e522052ca1cb703ea72b258a5a4718b34d5d1ea9c333d7a6778cead32cb902110000000291e13c04000000000000000000

1 output(s) for total of 0.600200000000 dcy

stealth address amount amount idx
00: 679e3f1a5e4c774addd9d8bcf76c6e3b664d3e39dedd891702dbd8d094a1c076 0.600200000000 1606853 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": 1124260, "vin": [ { "gen": { "height": 1124250 } } ], "vout": [ { "amount": 600200000, "target": { "key": "679e3f1a5e4c774addd9d8bcf76c6e3b664d3e39dedd891702dbd8d094a1c076" } } ], "extra": [ 1, 139, 22, 229, 34, 5, 44, 161, 203, 112, 62, 167, 43, 37, 138, 90, 71, 24, 179, 77, 93, 30, 169, 195, 51, 215, 166, 119, 140, 234, 211, 44, 185, 2, 17, 0, 0, 0, 2, 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