Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5ef995ba03ca0ee3fb1720bfb3c63a9b0d2e242caa8427e4fdeea360748bec5

Tx prefix hash: 10a74388398257763add21b1ef4a9551d3e4f0aa22e49687dc2c657a711edf88
Tx public key: a58fce62ddd00d6de81cfc40037b8b3bb71b9a6d5f6e39fdfa488b034632f4ae
Timestamp: 1578982726 Timestamp [UCT]: 2020-01-14 06:18:46 Age [y:d:h:m:s]: 05:024:00:28:49
Block: 45165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1167297 RingCT/type: yes/0
Extra: 01a58fce62ddd00d6de81cfc40037b8b3bb71b9a6d5f6e39fdfa488b034632f4ae02110000002a4943cd9f000000000000000000

1 output(s) for total of 434.860985945000 dcy

stealth address amount amount idx
00: dd04ab009db983c0a9c7134ba047aceaa066ebfc744abe074d5dd255bb5570b9 434.860985945000 82421 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": 45175, "vin": [ { "gen": { "height": 45165 } } ], "vout": [ { "amount": 434860985945, "target": { "key": "dd04ab009db983c0a9c7134ba047aceaa066ebfc744abe074d5dd255bb5570b9" } } ], "extra": [ 1, 165, 143, 206, 98, 221, 208, 13, 109, 232, 28, 252, 64, 3, 123, 139, 59, 183, 27, 154, 109, 95, 110, 57, 253, 250, 72, 139, 3, 70, 50, 244, 174, 2, 17, 0, 0, 0, 42, 73, 67, 205, 159, 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