Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34ccc4999a6ffe450eb11099b382890ead6a4c9eb1d81cf0293293d68a9ddb63

Tx prefix hash: 64bba79dd9af8d7b5d7d918d2bee3872b0ac7f858348b5c8b274327356d21c8f
Tx public key: d70f0a03145078fc99bc44f1ddc9f2240fb9f2d47f11da1b6afe39a8882416cc
Timestamp: 1587795617 Timestamp [UCT]: 2020-04-25 06:20:17 Age [y:d:h:m:s]: 05:194:09:43:02
Block: 96095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1308793 RingCT/type: yes/0
Extra: 01d70f0a03145078fc99bc44f1ddc9f2240fb9f2d47f11da1b6afe39a8882416cc02110000002f4ac5aa02000000000000000000

1 output(s) for total of 294.853059068000 dcy

stealth address amount amount idx
00: 3f940cb48b4d938d87719a1b7f1285bb7e2ecb8081e520c1e88592ebfb516e18 294.853059068000 170522 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": 96105, "vin": [ { "gen": { "height": 96095 } } ], "vout": [ { "amount": 294853059068, "target": { "key": "3f940cb48b4d938d87719a1b7f1285bb7e2ecb8081e520c1e88592ebfb516e18" } } ], "extra": [ 1, 215, 15, 10, 3, 20, 80, 120, 252, 153, 188, 68, 241, 221, 201, 242, 36, 15, 185, 242, 212, 127, 17, 218, 27, 106, 254, 57, 168, 136, 36, 22, 204, 2, 17, 0, 0, 0, 47, 74, 197, 170, 2, 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