Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d8a060860fab0d6f10b4b39ff69b2e966683da7ecc7446e09281fe154ece024

Tx prefix hash: dec8e61532167a2d7a6931991022fdd6cf784532299dfc34ef10e5fb80551934
Tx public key: 23d88d3a62f6c753e9314e00c624a19c9bdb82f9d61228b89c270853d3638150
Timestamp: 1719109591 Timestamp [UCT]: 2024-06-23 02:26:31 Age [y:d:h:m:s]: 00:314:09:43:14
Block: 1050153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224707 RingCT/type: yes/0
Extra: 0123d88d3a62f6c753e9314e00c624a19c9bdb82f9d61228b89c270853d36381500211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be7af2d2bae08fa9cd97612e15d5c2d0e42227ccbd8487674abac4aa8945bf47 0.600000000000 1520314 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": 1050163, "vin": [ { "gen": { "height": 1050153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be7af2d2bae08fa9cd97612e15d5c2d0e42227ccbd8487674abac4aa8945bf47" } } ], "extra": [ 1, 35, 216, 141, 58, 98, 246, 199, 83, 233, 49, 78, 0, 198, 36, 161, 156, 155, 219, 130, 249, 214, 18, 40, 184, 156, 39, 8, 83, 211, 99, 129, 80, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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