Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9bcebbf01c1e6e6a7625d017d69e81c840657d5fa37558c5982b3e5692246f5

Tx prefix hash: e1291357c1c303d149c893c31a62bb3908f68b8433cc94da551b6f9cf68e084f
Tx public key: 14397c20ef2797b67fe014939d6c91e872aa0e41ad8faa9216439c2df23b964a
Timestamp: 1710095323 Timestamp [UCT]: 2024-03-10 18:28:43 Age [y:d:h:m:s]: 01:267:20:57:15
Block: 975450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450204 RingCT/type: yes/0
Extra: 0114397c20ef2797b67fe014939d6c91e872aa0e41ad8faa9216439c2df23b964a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cf3cf884489bbf242215cbc829a58b9d5af27cb22336a013e1ac7961925ca6e 0.600000000000 1435421 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": 975460, "vin": [ { "gen": { "height": 975450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cf3cf884489bbf242215cbc829a58b9d5af27cb22336a013e1ac7961925ca6e" } } ], "extra": [ 1, 20, 57, 124, 32, 239, 39, 151, 182, 127, 224, 20, 147, 157, 108, 145, 232, 114, 170, 14, 65, 173, 143, 170, 146, 22, 67, 156, 45, 242, 59, 150, 74, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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