Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a93a1ddb89a1fe2c881d5df4cd766a41ae5f4af9a6157c2674b7e1808288863

Tx prefix hash: 6c1a09efe599cf8b706f2fd2882e80c05f25e106d9fa8c78844ccd90d2f3fcc0
Tx public key: fdad895fd7478620d7cf4a0f0eebb6af1e154499691f6bfd62596143be3bd81d
Timestamp: 1726053828 Timestamp [UCT]: 2024-09-11 11:23:48 Age [y:d:h:m:s]: 00:119:18:14:44
Block: 1107749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85646 RingCT/type: yes/0
Extra: 01fdad895fd7478620d7cf4a0f0eebb6af1e154499691f6bfd62596143be3bd81d021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33f2ba0622213e662b221026fccd301b4f749b7b6079d96b2d9e50afa1f25738 0.600000000000 1585394 of 15

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": 1107759, "vin": [ { "gen": { "height": 1107749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33f2ba0622213e662b221026fccd301b4f749b7b6079d96b2d9e50afa1f25738" } } ], "extra": [ 1, 253, 173, 137, 95, 215, 71, 134, 32, 215, 207, 74, 15, 14, 235, 182, 175, 30, 21, 68, 153, 105, 31, 107, 253, 98, 89, 97, 67, 190, 59, 216, 29, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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