Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31211064c9df8f06bf3ee78c44ec60bd7ee94da02719b6362e875a9bfcb93e3d

Tx prefix hash: 63e2e7f267c10d4389936e0503d9d53287752aaa54a4cde09d35adcbea94668a
Tx public key: 663253185178f2e39d5abaf3c89dbd069aa39f5dde79a29d53ef5eaf77051a4e
Timestamp: 1716491271 Timestamp [UCT]: 2024-05-23 19:07:51 Age [y:d:h:m:s]: 00:335:10:18:43
Block: 1028469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239753 RingCT/type: yes/0
Extra: 01663253185178f2e39d5abaf3c89dbd069aa39f5dde79a29d53ef5eaf77051a4e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac38f8a8e756935a44ce308faf5045b215d99cac0e0325d222ef97e053fa8ef9 0.600000000000 1496462 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": 1028479, "vin": [ { "gen": { "height": 1028469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac38f8a8e756935a44ce308faf5045b215d99cac0e0325d222ef97e053fa8ef9" } } ], "extra": [ 1, 102, 50, 83, 24, 81, 120, 242, 227, 157, 90, 186, 243, 200, 157, 189, 6, 154, 163, 159, 93, 222, 121, 162, 157, 83, 239, 94, 175, 119, 5, 26, 78, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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