Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f95a63904c743d9aa61b8e24cd47f6324b9d42373d042da17ede53fb89320f4

Tx prefix hash: e7b8256a584f09758643b7d43af335240aa83f66b4a65f89e50070078124a7e0
Tx public key: 104785e3f8ffcc4b54da69bf3379890d6c93c84bca289fbcba4571fd00cfb613
Timestamp: 1638145910 Timestamp [UCT]: 2021-11-29 00:31:50 Age [y:d:h:m:s]: 02:361:18:13:00
Block: 384304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 776567 RingCT/type: yes/0
Extra: 01104785e3f8ffcc4b54da69bf3379890d6c93c84bca289fbcba4571fd00cfb6130211000000084a0f5013000000000000000000

1 output(s) for total of 32.707073751000 dcy

stealth address amount amount idx
00: 8d74978f4a2e2c4bc7f9efd8afc1ace9ce8021775b37edb3d76f8bb507a94aed 32.707073751000 775711 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": 384314, "vin": [ { "gen": { "height": 384304 } } ], "vout": [ { "amount": 32707073751, "target": { "key": "8d74978f4a2e2c4bc7f9efd8afc1ace9ce8021775b37edb3d76f8bb507a94aed" } } ], "extra": [ 1, 16, 71, 133, 227, 248, 255, 204, 75, 84, 218, 105, 191, 51, 121, 137, 13, 108, 147, 200, 75, 202, 40, 159, 188, 186, 69, 113, 253, 0, 207, 182, 19, 2, 17, 0, 0, 0, 8, 74, 15, 80, 19, 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