Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78498af7336d31994b39ad7de345d918262c54d828228d9a19920e5e23dd52ec

Tx prefix hash: ea1b861d24ba538dfa6610fcbf6b1bceee31494b8c47f2b89f7491998e568357
Tx public key: c338cf2e37301d1a4f0d3c7584c35b6a537fd6b2e6f34d4f09815525d6c20f2e
Timestamp: 1576643232 Timestamp [UCT]: 2019-12-18 04:27:12 Age [y:d:h:m:s]: 05:023:15:03:12
Block: 28106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1164977 RingCT/type: yes/0
Extra: 01c338cf2e37301d1a4f0d3c7584c35b6a537fd6b2e6f34d4f09815525d6c20f2e02110000002e9159db1e000000000000000000

1 output(s) for total of 495.306491283000 dcy

stealth address amount amount idx
00: c63e5f00edef1d7d3e908c0992d2cf933872a7e96c42034b2ae3b5860083b2a7 495.306491283000 46628 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": 28116, "vin": [ { "gen": { "height": 28106 } } ], "vout": [ { "amount": 495306491283, "target": { "key": "c63e5f00edef1d7d3e908c0992d2cf933872a7e96c42034b2ae3b5860083b2a7" } } ], "extra": [ 1, 195, 56, 207, 46, 55, 48, 29, 26, 79, 13, 60, 117, 132, 195, 91, 106, 83, 127, 214, 178, 230, 243, 77, 79, 9, 129, 85, 37, 214, 194, 15, 46, 2, 17, 0, 0, 0, 46, 145, 89, 219, 30, 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