Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f94c66778041ef35ddceb8f6c768f2233d02d4ba8e9b7ed72471cd6bd71169d

Tx prefix hash: 18300175c42b6c51c60a7dc1923b1b89b2ec1e79ce9a66fba26f13197fc08175
Tx public key: ae2c3e6a3e9069b40868afb0b2eb77c4810c99a00b49f2131282d4c25484db60
Timestamp: 1715050462 Timestamp [UCT]: 2024-05-07 02:54:22 Age [y:d:h:m:s]: 00:248:13:03:24
Block: 1016525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177882 RingCT/type: yes/0
Extra: 01ae2c3e6a3e9069b40868afb0b2eb77c4810c99a00b49f2131282d4c25484db6002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5682ad3ceb9bb1b676aa085cdc572dd0009188f5748d1ab30f39d16187ac0ae8 0.600000000000 1480134 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": 1016535, "vin": [ { "gen": { "height": 1016525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5682ad3ceb9bb1b676aa085cdc572dd0009188f5748d1ab30f39d16187ac0ae8" } } ], "extra": [ 1, 174, 44, 62, 106, 62, 144, 105, 180, 8, 104, 175, 176, 178, 235, 119, 196, 129, 12, 153, 160, 11, 73, 242, 19, 18, 130, 212, 194, 84, 132, 219, 96, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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