Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98fc2ecd7b80242293f9dd8edb00e8b3226807b8592486bf4374f1b9d897a626

Tx prefix hash: 20be9476fe5aca21cd878a23b1705fd09a214cede07d6185159912297a82bf45
Tx public key: 7feaa0b60a23435684363a9d9eb970132f5b145d044a5f19b4193475101b753a
Timestamp: 1578972413 Timestamp [UCT]: 2020-01-14 03:26:53 Age [y:d:h:m:s]: 05:027:13:42:11
Block: 45107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1169825 RingCT/type: yes/0
Extra: 017feaa0b60a23435684363a9d9eb970132f5b145d044a5f19b4193475101b753a02110000000c8a2ee0d9000000000000000000

1 output(s) for total of 435.053457371000 dcy

stealth address amount amount idx
00: a62fe7519fa918f6c5ef5404e97bfbd73b6b4dd32ce06b6e41b1dc21e90384a0 435.053457371000 82299 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": 45117, "vin": [ { "gen": { "height": 45107 } } ], "vout": [ { "amount": 435053457371, "target": { "key": "a62fe7519fa918f6c5ef5404e97bfbd73b6b4dd32ce06b6e41b1dc21e90384a0" } } ], "extra": [ 1, 127, 234, 160, 182, 10, 35, 67, 86, 132, 54, 58, 157, 158, 185, 112, 19, 47, 91, 20, 93, 4, 74, 95, 25, 180, 25, 52, 117, 16, 27, 117, 58, 2, 17, 0, 0, 0, 12, 138, 46, 224, 217, 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