Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ce45965fe4c6360e91223c8020a91cd3e55fe02fcede169a32fc7d87fe9a19d

Tx prefix hash: e517a1a659825c52c4b54d474989cda3db2b04e6d72e9761fab8082f2cb8067d
Tx public key: d47ce343826f8f4c1a8d238c4dcdbfac875bc6f6798054b9e794942f688b85ab
Timestamp: 1721037032 Timestamp [UCT]: 2024-07-15 09:50:32 Age [y:d:h:m:s]: 00:285:04:03:13
Block: 1066160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203748 RingCT/type: yes/0
Extra: 01d47ce343826f8f4c1a8d238c4dcdbfac875bc6f6798054b9e794942f688b85ab021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3765a895fd897db49711c35721b593234f398810087ff63b612fd522fd7bac87 0.600000000000 1536733 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": 1066170, "vin": [ { "gen": { "height": 1066160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3765a895fd897db49711c35721b593234f398810087ff63b612fd522fd7bac87" } } ], "extra": [ 1, 212, 124, 227, 67, 130, 111, 143, 76, 26, 141, 35, 140, 77, 205, 191, 172, 135, 91, 198, 246, 121, 128, 84, 185, 231, 148, 148, 47, 104, 139, 133, 171, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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