Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e46552c176d8953655681451c3db82f402e4c87dff3b3c63561712bfa6a19f7f

Tx prefix hash: da7aa2457556235ad49aa0269982ddeff7e7e17ba2e2de53434467172efcf59c
Tx public key: af784e62880e4c4f86ac2274b12a451cf75b3d9dcff7206de47313280b6d8256
Timestamp: 1632143806 Timestamp [UCT]: 2021-09-20 13:16:46 Age [y:d:h:m:s]: 03:155:15:26:16
Block: 337554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 886995 RingCT/type: yes/0
Extra: 01af784e62880e4c4f86ac2274b12a451cf75b3d9dcff7206de47313280b6d8256021100000024fdc024ec000000000000000000

1 output(s) for total of 46.724418849000 dcy

stealth address amount amount idx
00: 70196acbfef510bdfcb1fa61c5f296a2b25f1be00f0d5819a5b10faedde88aa1 46.724418849000 695031 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": 337564, "vin": [ { "gen": { "height": 337554 } } ], "vout": [ { "amount": 46724418849, "target": { "key": "70196acbfef510bdfcb1fa61c5f296a2b25f1be00f0d5819a5b10faedde88aa1" } } ], "extra": [ 1, 175, 120, 78, 98, 136, 14, 76, 79, 134, 172, 34, 116, 177, 42, 69, 28, 247, 91, 61, 157, 207, 247, 32, 109, 228, 115, 19, 40, 11, 109, 130, 86, 2, 17, 0, 0, 0, 36, 253, 192, 36, 236, 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