Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4621e9547207e4de5ef89c507addba38439caaf36d16bb27dc3ad69d7a537569

Tx prefix hash: 698a465b060a77b320ffd63c8e93d7d9973f4bf6d385bcaec1d10ffc93e69a27
Tx public key: c0eee64de217f6acc962b96e53a218eb13aaa54e363c4c624ff5fa0f2c9c12cc
Timestamp: 1730570216 Timestamp [UCT]: 2024-11-02 17:56:56 Age [y:d:h:m:s]: 00:149:01:12:51
Block: 1145101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106362 RingCT/type: yes/0
Extra: 01c0eee64de217f6acc962b96e53a218eb13aaa54e363c4c624ff5fa0f2c9c12cc0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ebb969b0d8e9137a289672a4d171c5ccf5039217f7be0b14a18b3f03c9d4c99 0.600000000000 1629484 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": 1145111, "vin": [ { "gen": { "height": 1145101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ebb969b0d8e9137a289672a4d171c5ccf5039217f7be0b14a18b3f03c9d4c99" } } ], "extra": [ 1, 192, 238, 230, 77, 226, 23, 246, 172, 201, 98, 185, 110, 83, 162, 24, 235, 19, 170, 165, 78, 54, 60, 76, 98, 79, 245, 250, 15, 44, 156, 18, 204, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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