Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 940d7e24ef2eaa58c44e9cf8bf09d47bdac1904d64fb9301f14490f1947b9566

Tx prefix hash: de5ee63f57e4af8e6b3fa2ecd71f2e74d6489ca4935c06ebdc8b52664c928b5d
Tx public key: 82d2d4386541a4b18fb2197dbae84bf979bdf76c55a5387b04c9f45448ea58ad
Timestamp: 1706283721 Timestamp [UCT]: 2024-01-26 15:42:01 Age [y:d:h:m:s]: 01:031:01:24:51
Block: 943812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283260 RingCT/type: yes/0
Extra: 0182d2d4386541a4b18fb2197dbae84bf979bdf76c55a5387b04c9f45448ea58ad02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2ec2492bfb91a5c77e228a9b42c81f984473f97e6e0408985c866c62e27e794 0.600000000000 1402038 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": 943822, "vin": [ { "gen": { "height": 943812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2ec2492bfb91a5c77e228a9b42c81f984473f97e6e0408985c866c62e27e794" } } ], "extra": [ 1, 130, 210, 212, 56, 101, 65, 164, 177, 143, 178, 25, 125, 186, 232, 75, 249, 121, 189, 247, 108, 85, 165, 56, 123, 4, 201, 244, 84, 72, 234, 88, 173, 2, 17, 0, 0, 0, 7, 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