Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 759ec6d988b895273fc8ba8e2851e1748306fd6a706fb9b71470461ef3af01b8

Tx prefix hash: 69502660e7b82f8d86a1460a9ce594fb4a9c10e22d023a0cb3a3032db0bd68bb
Tx public key: 9b5a4b0a291b7fab1625118a573a8a931540928566fb09e9f4bceabdd75e5e57
Timestamp: 1581568314 Timestamp [UCT]: 2020-02-13 04:31:54 Age [y:d:h:m:s]: 04:325:13:01:06
Block: 63842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1124896 RingCT/type: yes/0
Extra: 019b5a4b0a291b7fab1625118a573a8a931540928566fb09e9f4bceabdd75e5e5702110000000103d36d11000000000000000000

1 output(s) for total of 377.108016468000 dcy

stealth address amount amount idx
00: 4eb6c75a86c3e2444938f53ad9f81fbe5551c37ff5923aa1a02efdb7542c1ea6 377.108016468000 117698 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": 63852, "vin": [ { "gen": { "height": 63842 } } ], "vout": [ { "amount": 377108016468, "target": { "key": "4eb6c75a86c3e2444938f53ad9f81fbe5551c37ff5923aa1a02efdb7542c1ea6" } } ], "extra": [ 1, 155, 90, 75, 10, 41, 27, 127, 171, 22, 37, 17, 138, 87, 58, 138, 147, 21, 64, 146, 133, 102, 251, 9, 233, 244, 188, 234, 189, 215, 94, 94, 87, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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