Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81d5948a70b972544b8040174bc65e60ba3c78cac672389eaf4900a00f3c84f3

Tx prefix hash: d9896492a37e9bc001e99a19fac0c63c6f11b48f7aa463bf6e991857613d75cb
Tx public key: cbbbad8e0b32ef197aa8c653eb45f9d11a416c3f8649436c1b4df25f3a2468fa
Timestamp: 1702229789 Timestamp [UCT]: 2023-12-10 17:36:29 Age [y:d:h:m:s]: 01:337:02:28:07
Block: 910230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499791 RingCT/type: yes/0
Extra: 01cbbbad8e0b32ef197aa8c653eb45f9d11a416c3f8649436c1b4df25f3a2468fa021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46b5977582c85105e994dc6a3df9938363f503d113680ef0ad43c38cf64d3840 0.600000000000 1367375 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": 910240, "vin": [ { "gen": { "height": 910230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46b5977582c85105e994dc6a3df9938363f503d113680ef0ad43c38cf64d3840" } } ], "extra": [ 1, 203, 187, 173, 142, 11, 50, 239, 25, 122, 168, 198, 83, 235, 69, 249, 209, 26, 65, 108, 63, 134, 73, 67, 108, 27, 77, 242, 95, 58, 36, 104, 250, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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