Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d85aa052ef90603e19775e2fe141d819a1484b34946fe3c2796f3f30b2e313da

Tx prefix hash: 095bcac3a0f10d1155546efca97edb0ddce8a2b0bafec04a44169504837b3a46
Tx public key: a8433f427facb9f9aa345e38f81a8081a4df34e7be6c1180e31fa8e5b7a3d3f4
Timestamp: 1695423627 Timestamp [UCT]: 2023-09-22 23:00:27 Age [y:d:h:m:s]: 01:188:10:28:08
Block: 854002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395741 RingCT/type: yes/0
Extra: 01a8433f427facb9f9aa345e38f81a8081a4df34e7be6c1180e31fa8e5b7a3d3f4021100000003faf35c9c000000000000000000

1 output(s) for total of 0.908525061000 dcy

stealth address amount amount idx
00: 032ecece92e9144663b6c45584ee3981f8b95dc9155737259089c2f33fd609c3 0.908525061000 1307952 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": 854012, "vin": [ { "gen": { "height": 854002 } } ], "vout": [ { "amount": 908525061, "target": { "key": "032ecece92e9144663b6c45584ee3981f8b95dc9155737259089c2f33fd609c3" } } ], "extra": [ 1, 168, 67, 63, 66, 127, 172, 185, 249, 170, 52, 94, 56, 248, 26, 128, 129, 164, 223, 52, 231, 190, 108, 17, 128, 227, 31, 168, 229, 183, 163, 211, 244, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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