Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3656dde7a662f879db6e5de90f008901d4cbb936a47035e1d8cb39ba541f8f8b

Tx prefix hash: 289aa8bf4802178639e4a6242891ae5a0f398d820ad9cf277a91e7e8bde18a18
Tx public key: 7fc7f69f07dfccfcd1a06982056121f7f346a3ed39929dec411f0fe9df8d9e1e
Timestamp: 1736666128 Timestamp [UCT]: 2025-01-12 07:15:28 Age [y:d:h:m:s]: 00:159:13:30:58
Block: 1195580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113700 RingCT/type: yes/0
Extra: 017fc7f69f07dfccfcd1a06982056121f7f346a3ed39929dec411f0fe9df8d9e1e0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f3455892f3baa091cd8f2a08602766e2083c9e70fd29d614298f37e0b17fcfb 0.600000000000 1682171 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": 1195590, "vin": [ { "gen": { "height": 1195580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f3455892f3baa091cd8f2a08602766e2083c9e70fd29d614298f37e0b17fcfb" } } ], "extra": [ 1, 127, 199, 246, 159, 7, 223, 204, 252, 209, 160, 105, 130, 5, 97, 33, 247, 243, 70, 163, 237, 57, 146, 157, 236, 65, 31, 15, 233, 223, 141, 158, 30, 2, 17, 0, 0, 0, 2, 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