Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e61bd84d2a7e82597e481926e5923e6771a9cdd122d87375197f8f9e844c08d5

Tx prefix hash: ba6b9896d5f8bc54c8d076b760c7aeb91a18c4fec1772deee0e638994b4bdc80
Tx public key: da055101e8f36107e853d0136ac82f635e74120f11e726d083229b2e98f71092
Timestamp: 1733538521 Timestamp [UCT]: 2024-12-07 02:28:41 Age [y:d:h:m:s]: 00:118:01:51:19
Block: 1169695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84184 RingCT/type: yes/0
Extra: 01da055101e8f36107e853d0136ac82f635e74120f11e726d083229b2e98f710920211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c7f3bc082c2e96d94ac0d5170de079b3d6050a229aa2cd592bc1bd6d7eae25c 0.600000000000 1655418 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": 1169705, "vin": [ { "gen": { "height": 1169695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c7f3bc082c2e96d94ac0d5170de079b3d6050a229aa2cd592bc1bd6d7eae25c" } } ], "extra": [ 1, 218, 5, 81, 1, 232, 243, 97, 7, 232, 83, 208, 19, 106, 200, 47, 99, 94, 116, 18, 15, 17, 231, 38, 208, 131, 34, 155, 46, 152, 247, 16, 146, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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